VLANs don't exist. They're a concept. NICs don't support or not support vlans. Neither do computers or operating systems. That's like saying "My NIC supports a destination MAC address field." It's a meaningless statement.

A "vlan" is a field in an L2 frame. It has either a value of 0 (untagged) or some non-zero value (the vlan ID).

A NIC, when connected, sees every single frame that appears at its input port. All of them. Every single one. It doesn't matter what's in the frame. It doesn't matter what the source or destination address is. It doesn't matter what the vlan ID tag field is set to. The NIC sees every single frame.

For hardware, firmware, or software to decide if the frame should be processed further, it must first accept the frame (obviously, right?) and decode enough of it to determine if further processing is warranted. If the destination MAC doesn't match, the frame is discarded. (Ignore broadcasts here for the sake of clarity. But they're just another "acceptable" destination MAC.)

If you tell the NIC's software to pass along every frame it sees, you get what's called "promiscuous" mode. That means the hardware/firmware/software built into the NIC doesn't do any filtering or make any decisions about the traffic. That's how wireshark works.

If other hardware or software defines rules for passing frames, your device has to follow those rules if you want your hardware or software to see the traffic.But there's no myth or magic involved.